Cloud rules and alerting framework

ABSTRACT

Systems, methods, and computer-readable media having computer-executable instructions embodied thereon for providing cloud rules and an alerting framework are provided. In embodiments, one or more rules associated with one or more healthcare information systems are received. The one or more rules each designate an initiating and at least one target application. One or more actions are associated to each target application. The initiating application is monitored for a trigger associated with the one or more rules. In embodiments, the trigger causes the one or more actions to be communicated to each target applications. In embodiments, the one or more actions initiate various changes in a display associated with each target application.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/796,151, filed Oct. 27, 2017, which is hereby incorporated byreference in its entirety.

BACKGROUND

In recent years, healthcare service providers have been making thetransition from manual paper-based medical records to an electronicformat. Commercially available computer software, such as PowerChart®,PowerChart Office®, and other Cerner Millennium® applications marketedby Cerner Corporation of Kansas City, Mo. have advanced the state of theart well beyond the conventional manual approach. Electronic-basedrecords substantially increase the efficiency of healthcare providersand institutions. Electronic medical records also substantially reducerisks associated with high volumes of patient data and potentialliabilities arising out of clerical errors or misinformation. Theelectronic format enhances communication between various providers andwithin institutions. As electronic clinical documentation continues tobecome increasingly prevalent, the variety of applications, electronicforms, electronic charts, and user interfaces, as well as thecorresponding versatility of this format, continue to expand.

Many actions performed in various workflows for a particular departmentor area in a healthcare facility directly impact other workflows andneed to be communicated to other teams and providers. Typically, this isaddressed through alerts via text messaging, email, or direct manualcommunication. Unfortunately, these alerts are often overlooked becausethey are not embedded into the application utilized by each departmentof the healthcare facility. In many cases, such embedding is not evenpossible because different solutions, offerings, and systems are used byeach department. Thus, there is no integration or adequate real-timecommunication between departments and direct impact of the display of aparticular application based on a rule or trigger by another cannot beachieved.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Embodiments of the present invention relate to systems, methods, andcomputer-readable media having computer-executable instructions embodiedthereon for performing a method in a computerized healthcare system toprovide a cloud rules and alerting framework. In one embodiment, one ormore computer storage media having computer-executable instructionsembodied thereon, that when executed by one or more computing devices,cause the one or more computing devices to perform a method of providingcloud rules and an alerting framework. The method includes receiving oneor more rules associated with one or more healthcare informationsystems. The one or more rules each designate an initiating and at leastone target application. One or more actions are associated to the atleast one target application. The initiating application is monitoredfor a trigger associated with the one or more rules.

In one embodiment, a system for providing cloud rules and an alertingframework is provided. The system comprises a processor coupled to acomputer-storage medium, the computer-storage medium having storedthereon a plurality of computer software components executable by theprocessor. The computer software components include a rule component forreceiving one or more rules associated with one or more healthcareinformation systems. The one or more rules each designate an initiatingand at least one target application. An association component associatesone or more actions to the at least one target application. A monitoringcomponent monitors the initiating application for a trigger associatedwith the one or more rules. A trigger component receives the triggerassociated with the one or more rules. A communication componentcommunicates the one or more actions to the at least one targetapplication.

In one embodiment, one or more computer storage media havingcomputer-executable instructions embodied thereon, that when executed byone or more computing devices, cause the one or more computing devicesto perform a method for providing cloud rules and an alerting framework.The method includes subscribing a target application to an alertingframework. The alerting framework includes one or more rules. One ormore actions are configured to execute on the target application whenthe target application receives communication from the alertingframework that the one or more rules are satisfied. The one or moreactions are executed on the target application.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The present invention is described in detail below with reference to theattached drawing figures, wherein:

FIG. 1 is a block diagram of an exemplary computing system suitable foruse in implementing embodiments of the present invention;

FIG. 2 schematically shows a network environment suitable for performingembodiments of the invention.

FIG. 3 is a flow diagram showing an exemplary method for providing cloudrules and an alerting framework, in accordance with an embodiment of thepresent invention;

FIG. 4 is a flow diagram showing an exemplary method for providing cloudrules and an alerting framework, in accordance with an embodiment of thepresent invention; and

FIGS. 5A-7B are illustrative screen displays illustrating variouschanges in displays associated with various target applications, inaccordance with embodiments of the present invention.

DETAILED DESCRIPTION

The subject matter of the present invention is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step” and/or “block” may be used herein to connotedifferent components of methods employed, the terms should not beinterpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly described.

Embodiments of the present invention provide systems, methods, andcomputer-readable media having computer-executable instructions embodiedthereon for providing cloud rules and an alerting framework. Anexemplary operating environment is described below, though one ofordinary skill in the art will appreciate that other suitable operatingenvironments may be used.

Having briefly described embodiments of the present invention, anexemplary operating environment suitable for use in implementingembodiments of the present invention is described below. Referring nowto the drawings in general, and initially to FIG. 1 in particular, anexemplary computing system environment, for instance, a medicalinformation computing system, on which embodiments of the presentinvention may be implemented is illustrated and designated generally asreference numeral 20. It will be understood and appreciated by those ofordinary skill in the art that the illustrated medical informationcomputing system environment 20 is merely an example of one suitablecomputing environment and is not intended to suggest any limitation asto the scope of use or functionality of the invention. Neither shouldthe medical information computing system environment 20 be interpretedas having any dependency or requirement relating to any single componentor combination of components illustrated therein.

Embodiments of the present invention may be operational with numerousother general purpose or special purpose computing system environmentsor configurations. Examples of well-known computing systems,environments, and/or configurations that may be suitable for use withthe present invention include, by way of example only, personalcomputers, server computers, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of theabove-mentioned systems or devices, and the like.

Embodiments of the present invention may be described in the generalcontext of computer-executable instructions, such as program modules,being executed by a computer. Generally, program modules include, butare not limited to, routines, programs, objects, components, and datastructures that perform particular tasks or implement particularabstract data types. Embodiments of the present invention may also bepracticed in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules may be located in local and/or remote computer storage mediaincluding, by way of example only, memory storage devices.

With continued reference to FIG. 1, the exemplary medical informationcomputing system environment 20 includes a general purpose computingdevice in the form of a server 22. Components of the server 22 mayinclude, without limitation, a processing unit, internal system memory,and a suitable system bus for coupling various system components,including database cluster 24, with the server 22. The system bus may beany of several types of bus structures, including a memory bus or memorycontroller, a peripheral bus, and a local bus, using any of a variety ofbus architectures. By way of example, and not limitation, sucharchitectures include Industry Standard Architecture (ISA) bus, MicroChannel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronic Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus, also known as Mezzanine bus.

The server 22 typically includes, or has access to, a variety ofcomputer readable media, for instance, database cluster 24. Computerreadable media can be any available media that may be accessed by server22, and includes volatile and nonvolatile media, as well as removableand non-removable media. By way of example, and not limitation, computerreadable media may include computer storage media and communicationmedia. Computer storage media may include, without limitation, volatileand nonvolatile media, as well as removable and nonremovable mediaimplemented in any method or technology for storage of information, suchas computer readable instructions, data structures, program modules, orother data. In this regard, computer storage media may include, but isnot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVDs) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage, orother magnetic storage device, or any other medium which can be used tostore the desired information and which may be accessed by the server22. Communication media typically embodies computer readableinstructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave or other transportmechanism, and may include any information delivery media. As usedherein, the term “modulated data signal” refers to a signal that has oneor more of its attributes set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared, and other wireless media. Combinations of any of the abovealso may be included within the scope of computer readable media.

The computer storage media discussed above and illustrated in FIG. 1,including database cluster 24, provide storage of computer readableinstructions, data structures, program modules, and other data for theserver 22. For example, the database cluster 24 can contain electronicclinical documents capable of receiving multiple types of input,including images, dictation audio input, structured user input,free-text input, and system-generated input. Database cluster 24 cancontain electronic medical records for various patients. Data from theserecords can be used by the system to generate system-generated input tobe received as a trigger into an alerting framework. And, electronicclinical documents that have been populated with various forms of inputcan be stored in database cluster 24.

The server 22 may operate in a computer network 26 using logicalconnections to one or more remote computers 28. Remote computers 28 maybe located at a variety of locations in a medical or researchenvironment, for example, but not limited to, clinical laboratories,hospitals and other inpatient settings, veterinary environments,ambulatory settings, medical billing and financial offices, hospitaladministration settings, home health care environments, and clinicians'offices. Clinicians may include, but are not limited to, a treatingphysician or physicians, specialists such as surgeons, radiologists,cardiologists, and oncologists, emergency medical technicians,physicians' assistants, nurse practitioners, nurses, nurses' aides,pharmacists, dieticians, microbiologists, laboratory experts, geneticcounselors, researchers, veterinarians, students, and the like. Theremote computers 28 may also be physically located in non-traditionalmedical care environments so that the entire health care community maybe capable of integration on the network. The remote computers 28 may bepersonal computers, servers, routers, network PCs, peer devices, othercommon network nodes, or the like, and may include some or all of thecomponents described above in relation to the server 22. The devices canbe personal digital assistants or other like devices.

Exemplary computer networks 26 may include, without limitation, localarea networks (LANs) and/or wide area networks (WANs). Such networkingenvironments are commonplace in offices, enterprise-wide computernetworks, intranets, and the Internet. When utilized in a WAN networkingenvironment, the server 22 may include a modem or other means forestablishing communications over the WAN, such as the Internet. In anetworked environment, program modules or portions thereof may be storedin the server 22, in the database cluster 24, or on any of the remotecomputers 28. For example, and not by way of limitation, variousapplication programs may reside on the memory associated with any one ormore of the remote computers 28. It will be appreciated by those ofordinary skill in the art that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers (e.g., server 22 and remote computers 28) may be utilized.

In operation, a user may enter commands and information into the server22 or convey the commands and information to the server 22 via one ormore of the remote computers 28 through input devices, such as akeyboard, a pointing device (commonly referred to as a mouse), atrackball, or a touch pad. Other input devices may include, withoutlimitation, image capturing devices, microphones, satellite dishes,scanners, or the like. Commands and information may be sent directlyfrom a remote healthcare device to the server 22. In accordance withvarious embodiments of the present invention, commands and informationmay also be sent directly from an image capturing device to the server22, and vice versa. In addition to a monitor, the server 22 and/orremote computers 28 may include other peripheral output devices, such asspeakers and a printer.

Although many other internal components of the server 22 and the remotecomputers 28 are not shown, those of ordinary skill in the art willappreciate that such components and their interconnections are wellknown. Accordingly, additional details concerning the internalconstruction of the server 22 and the remote computers 28 are notfurther disclosed herein.

The electronic clinical document can be provided via any type ofgraphical display, such as a computer monitor or any other type ofgraphical presentation apparatus, such as for example, an LCD screen, alaptop display, or a handheld PDA device. An electronic clinicaldocument can be any type of electronic medical documentation relevant toa particular patient or area of the healthcare facility and can be partof an electronic healthcare information technology system. An electronicclinical document can also be a clinical event document relating to aparticular clinical event for a patient, including, by way of exampleonly, a patient visit or encounter. By way of example and notlimitation, electronic clinical documents may be images, clinical notes,summaries, reports, analyses, or other types of electronic medicaldocumentation relevant to a particular patient's condition and/ortreatment. Electronic clinical documents contain various types ofinformation relevant to the condition and/or treatment of a particularpatient and can include information relating to, for example, patientidentification information, images, physical examinations, vital signs,past medical histories, surgical histories, family histories, historiesof present illnesses, current and past medications, allergies, symptoms,past orders, completed orders, pending orders, tasks, lab results, othertest results, patient encounters and/or visits, immunizations, physiciancomments, nurse comments, other caretaker comments, and a host of otherrelevant clinical information. Electronic clinical documents may bestored within an overall electronic medical chart or electronic medicalrecord associated with a patient.

The format for electronic clinical documents may be customized by theuser and/or may be established by a particular healthcare institution,such as by using a profile stored in a database, such as databasecluster 24, or by using a locally stored profile on a remote computer(e.g., remote computer 28 of FIG. 1).

Referring now to FIG. 2, a block diagram is provided illustrating anexemplary system 200 in which an alerting framework 210 is showncommunicatively coupled, such as via a network, to two healthcareinformation systems 230,234, in accordance with an embodiment of thepresent invention. Each healthcare information system 230,234 iscommunicatively coupled, such as via a network, to remote computers232,236. It should be understood that any number of healthcareinformation systems can be connected to the alerting framework 210. Itshould also be understood that any number of remote computers 232,236can be connected to each healthcare information system 230,234. Thealerting framework 210, the healthcare information systems 230,234, andthe remote computers 232,236 may be part of a comprehensive computingsystem within a clinical environment similar to the exemplary computingsystem 20 discussed above with reference to FIG. 1.

The alerting framework 210 may include a database (not shown) storingdata communicated by the healthcare information systems 230,234 and theremote computers 232,236. Each healthcare information system 230,234 mayalso include a database (not shown) storing data communicated by theremote computers 232,236 or various medical devices (not shown). Thealerting framework 210 is comprised of various components, includingrule component 212, association component 214, monitoring component 216,trigger component 218, and communication component 220. In variousembodiments, the alerting framework 210 includes display component 22,workflow component 224, lock component 226, deactivation component 228,cease component 229.

Rule component 212 receives one or more rules associated with one ormore healthcare information systems. The one or more rules eachdesignate an initiating and at least one target application. Forexample, the initiating application may be system 230 and the targetapplication may be system 234. In addition to designating the initiatingapplication, the one or more rules may establish a condition, setting,or threshold that must be met by the initiating application. In thisrespect, the condition, setting, or threshold corresponds to a triggerassociated with the one or more rules.

Association component 214 associates one or more actions to the at leastone target application. The one or more actions correspond to actionsthe target application takes when the condition, setting, or thresholdis met by the initiating application. In one embodiment, the one or moreactions initiates a change in a display associated with the at least onetarget application. In one embodiment, the change in display is a changein the background color of the at least one target application. In oneembodiment, the change in display causes the at least one targetapplication to flash a specific color or icon on the display. In oneembodiment, the one or more actions initiate custom changes to eachtarget application. In one embodiment, the one or more actions initiatesa change in a workflow associated with the at least one targetapplication. In one embodiment, the one or more actions cause the atleast one target application to be locked until corrective action istaken.

Monitor component monitors 216 the initiating application for a triggerassociated with the one or more rules. The trigger indicates that thecondition, setting, or threshold has been met by the initiatingapplication. Trigger component 218 receives the trigger associated withthe one or more rules. Communication component 220 communicates the oneor more actions to the at least one target application.

In one embodiment, display component 222 changes a display for the atleast one target application. For example, in one embodiment, displaycomponent 222 changes the background color of the at least one targetapplication to immediately captures the attention of and alerts theresponsible clinician. In another embodiment, display component 222causes the at least one target application to flash a specific color,icon, or text on the display.

In one embodiment, workflow component 224 initiates a change in aworkflow associated with the at least one target application. Thiscauses display component 222 to display a modified workflow associatedwith the at least one target application that is based on the condition,setting or threshold met by the initiating application.

In one embodiment, lock component 226 locks the at least one targetapplication until corrective action is taken. This prevents a clinicianfrom taking any action within the target application other than one thatcorrects the current condition, setting, or threshold that has been metby the initiating application. Such corrective action may be simplycharting a particular item within the target application. Or thecorrective action may require the clinician to administer, order, ordispense a particular medication or treatment to the patient.

In one embodiment, deactivation component 228 receives a deactivationtrigger for the one or more rules. In one embodiment, the deactivationtrigger indicates that the condition, setting, or threshold is no longermet by the initiating application. In another embodiment, thedeactivation trigger indicates that the appropriate corrective actionhas been taken by the at least one target application. It should beappreciated that a deactivation trigger may be received for only one ofthe at least one target applications. For example, when correctiveaction is required, one of the at least one target applications maysatisfy this requirement before another. Thus, the one that has alreadysatisfied the requirement may communicate the deactivation trigger todeactivation component 228. Once the deactivation trigger is received bydeactivation component 228, cease component 229 communicates to the atleast one target application to cease the one or more actions.

With reference to FIG. 3, an exemplary flow diagram representative of amethod for providing cloud rules and an alerting framework in accordancewith an embodiment of the present invention is shown and referencedgenerally by reference numeral 300. Method 300 may be implemented usingthe above-described exemplary computing system environment (FIG. 1) and,by way of example only, may be utilized by a healthcare facility tocommunicate alerts across all healthcare information systems supportinga particular patient. The terms “individual”, “person”, and “patient”are used interchangeably herein and are not meant to limit the nature ofthe referenced individual in any way. Rather, the methods and systemsdescribed herein are equally applicable in, for instance, a veterinarysetting.

Initially, as shown at step 310, one or more rules associated with oneor more healthcare information systems is received. The one or morerules each designate an initiating and at least one target application.One or more actions are associated, at step 320, to the at least onetarget application. At step 330, the initiating application is monitoredfor a trigger associated with the one or more rules. The triggercorresponds to a condition, setting, or threshold in the initiatingapplication. When the condition, setting, or threshold is met, theinitiating application communicates the trigger to the alertingframework.

In one embodiment, a trigger associated with the one or more rules isreceived. Once the trigger is received, the alerting frameworkidentifies the one or more rules associated with the trigger. Thealerting framework also identifies the one or more actions associated tothe at least one target application. In one embodiment, the one or moreactions are communicated to the at least one target application.

In one embodiment, the one or more actions initiates a change in adisplay associated with the at least one target application. In oneembodiment, the change in display is a change in the background color ofthe at least one target application. In one embodiment, the change indisplay causes the at least one target application to flash a specificcolor or icon on the display. In one embodiment, the one or more actionsinitiate custom changes to each target application. The custom changesallow a user of a particular target application to tailor the change indisplay to that target application, such that the change in display isnoticeable to the user. In this respect, the one or more actions may bedifferent for each target application.

In one embodiment, the one or more actions initiates a change in aworkflow associated with the at least one target application. The changein the workflow allows a clinician to promptly provide the proper carefor a patient. For example, the clinician may be instructed to documentmore or less frequently or may be instructed to administer or order amedication. The change in the workflow also is important to thehealthcare facility for reimbursement purposes. For example, if apatient receives a particular treatment, workflows must be followedproperly in order for the healthcare facility to receive fullreimbursement for that treatment. The alerting framework provides apersistent change in the visual presentation of other associated systemsacross the healthcare facility.

In one embodiment, the one or more actions cause the at least one targetapplication to be locked until corrective action is taken. This forces aclinician responsible for the target application to take correctiveaction before any additional action can be taken within the targetapplication. Such corrective action may be to acknowledge an alert,order or administer a medication, document information, or perform anaction corresponding to the workflow or a change in the workflow.

In one embodiment, a deactivation trigger for the one or more rules isreceived. In one embodiment, the alerting framework communicates to theat least one target application to cease the one or more actions. Thus,as can be appreciated, the alerting framework provides a persistentchange to the at least one target application until the deactivationtrigger is received. The deactivation trigger is received, in oneembodiment, when the initiating application communicates to the alertingframework that the condition, setting, or threshold within theinitiating application is no longer met. In another embodiment, thedeactivation trigger is received when a corresponding action is taken onone of the at least one target applications. In another embodiment, thedeactivation trigger is received when all corresponding actions aretaken an all of the at least one target applications.

Referring now to FIG. 4, an exemplary flow diagram representative of amethod for providing cloud rules and an alerting framework in accordancewith an embodiment of the present invention is shown and referencedgenerally by reference numeral 400. Method 400 may be implemented usingthe above-described exemplary computing system environment (FIG. 1) and,by way of example only, may be utilized for protocol driven imageacquisition.

Initially, as shown at step 410, a target application subscribes to analerting framework. The alerting framework includes one or more rules.The one or more rules correspond to a condition, setting, or thresholdin an initiating application. One or more actions to execute on thetarget application are configured at step 420, when the targetapplication receives communication from the alerting framework that theone or more rules are satisfied. The one or more actions are executed,at step 430, on the target application.

In one embodiment, the one or more actions initiate a change in adisplay associated with the target application. In one embodiment, theone or more actions initiate a change in a workflow associated with thetarget application. In one embodiment, the target application receives anotification that the alerting framework received a deactivation triggerand the one or more actions are ceased on the target application.

Referring now to FIGS. 5A-7B, illustrative screen displays 500,600,700illustrate various changes in displays associated with various targetapplications, in accordance with embodiments of the present invention.For example, a typical anesthesia record, a typical nursing record, anda typical perioperative tracking display for a patient about to beconnected to a cardiac pump is displayed in FIGS. 5A, 6A, and 7A,respectively. Once the surgeon connects the pump to the patient and theperfusionist starts the bypass machine, a trigger is generated. Thetrigger can be generated from the bypass machine itself or in accordancewith documentation by the perfusionist. This trigger is received by thealerting framework and communicated to associated systems. Theanesthesia system subscribes to this alert because once the patient ison the pump, the anesthesiologist no longer ventilates the patient sincethe perfusionist is already oxygenating the patient's lungs via thepump. So the anesthesia system is configured to change the display 500accordingly, as illustrated by FIG. 5B. In this example, the background510 of the display changes color and the patient's name 520 isprominently displayed across the screen so the anesthesiologist isimmediately aware of the patient's condition.

Similarly, the nurse needs to document the patient's current condition.The display 600 changes accordingly, as illustrated by FIG. 6B, to alertthe nurse of the change in the patient's status. In this example, note610 is displayed in the demographics bar. As illustrated by FIG. 7B, theperioperative tracking display 700 is also changed to reflect the changein the patient's status. In this example, the status 710 is updated toreflect the current status of the patient. In addition, the backgroundcolor 720 of the status section is also changed to make it readilyapparent to any clinician monitoring the status of the patient withinthis system.

As can be understood, the present invention provides systems, methods,and user interfaces for providing cloud rules and an alerting framework.The present invention has been described in relation to particularembodiments, which are intended in all respects to be illustrativerather than restrictive. Alternative embodiments will become apparent tothose of ordinary skill in the art to which the present inventionpertains without departing from its scope.

From the foregoing, it will be seen that this invention is one welladapted to attain all the ends and objects set forth above, togetherwith other advantages which are obvious and inherent to the system andmethod. It will be understood that certain features and subcombinationsare of utility and may be employed without reference to other featuresand subcombinations. This is contemplated and within the scope of theclaims.

The invention claimed is:
 1. A method of causing display via a sharedalerting framework, the method comprising: causing a first displaydevice to display first information associated with a first patient;causing a second display device to display second information associatedwith the first patient, wherein the first display device and the seconddisplay device are associated to a same alerting framework; detecting atrigger associated with an application that is indicative of a change instatus of the first patient; and based at least in part on the detectingof the trigger and the first display device and the second displaydevice being associated to the same alerting framework, automaticallycausing the first display device to modify a display of at least aportion of the first information and the second display device to modifya display of at least a portion of the second information.
 2. The methodof claim 1, wherein the modifying of the display of the first displaydevice includes changing a background color and changing a size of thefirst patient's name.
 3. The method of claim 1, wherein the modifying ofthe display of the second display device includes generating, inresponse to the detecting of the trigger, a note indicative of thechange in status of the first patient.
 4. The method of claim 1, whereinthe first information of the first display device is included in a userinterface, the user interface including a plurality of elements, andwherein the modifying of the display of the first display deviceincludes generating indicia to an element of the plurality of elements,and wherein a format of the plurality of elements do not change inresponse to the modifying of the display of the first display device. 5.The method of claim 1, wherein the first display device does not includeany applications that are integrated with any other application runningon the second display device except through the same alerting framework.6. The method of 1, wherein the modifying of the display of the firstdisplay device includes locking a first application within the firstdisplay device that is indicative of preventing a clinician from takingany action within the first application.
 7. The method of claim 1,wherein the modifying of the display of the first display device ceasesin response to one or more rules associated with the trigger no longerbeing met, the ceasing is indicative of the status of the first patientno longer being in a changed state.
 8. One or more computer storagemedia having computer executable instructions embodied thereon, thatwhen executed by one or more computing devices, cause the one or morecomputing devices to perform a method, the method comprising: causing afirst display device to display first information associated with afirst application; causing a second display device to display secondinformation associated with a second application, wherein the firstdisplay device and the second display device are associated to a samealerting framework in one or more healthcare information systems;receiving indication that a trigger associated with one or more ruleshas been detected; and based at least in part on the received indicationand the first display device and the second display device beingassociated to the same alerting framework, automatically causing thefirst display device to modify a display of at least a portion of thefirst information and the second display device to modify a display ofat least a portion of the second information.
 9. The media of claim 8,wherein the modifying of the display of the first display deviceincludes changing a workflow of the first application that is indicativeof instructing a user to change one or more actions associated withtreatment.
 10. The media of claim 8, wherein the modifying of thedisplay of the second display device includes generating, in response tothe receiving of the indication of the detected trigger, a noteindicative of the change in status of the first patient.
 11. The mediaof claim 8, wherein the first information of the first display device isincluded in a user interface, the user interface including a pluralityof elements, and wherein the modifying of the display of the firstdisplay device includes changing indicia in a field within an element ofthe plurality of elements from first indicia to second indicia.
 12. Themedia of claim 8, wherein the first application and the secondapplication are not integrated except through the same alertingframework.
 13. The media of claim 8, wherein the modifying of thedisplay of the first display device includes locking the firstapplication within the first display device that is indicative ofpreventing a clinician from taking any action within the firstapplication, wherein the second application is not locked such thatanother clinician may take any action within the second application. 14.The media of claim 8, wherein the modifying of the display of the firstdisplay device ceases in response to the one or more rules no longerbeing met, the ceasing is indicative of the status of the first patientno longer being in a changed state.
 15. A system comprising one or moreprocessors coupled to one or more computer-storage devices, thecomputer-storage devices having stored thereon computer executableinstructions that, when executed by the one or more processors, causethe one or more processors to perform a method, the method comprising:displaying, within a first display device, first information associatedwith a first application, wherein the first display device is one of aplurality of display devices included in a healthcare facility, andwherein the plurality of display devices are associated to a samealerting framework, and wherein the first application is not integratedwith any other application of the plurality of display devices exceptthrough the same alerting framework; receiving indication that a triggerassociated with one or more rules has been detected; and based at leastin part on the receiving of the indication and the plurality of displaydevices being associated to the same alerting framework, automaticallymodifying display of the first information within the first displaydevice.
 16. The system of claim 15, wherein the modifying displayincludes changing a color of a background of a user interface associatedwith the first application.
 17. The system of claim 15 wherein themodifying display includes generating, in response to the receiving ofthe indication that a trigger has been detected, a note indicative ofthe change in status of a first patient within the healthcare facility.18. The system of claim 15, wherein the first information of the firstdisplay device is included in a user interface, the user interfaceincluding a plurality of elements, and wherein the modifying display ofthe first display device includes changing color in a field within anelement of the plurality of elements from a first color to a secondcolor.
 19. The system of claim 15, wherein the modifying display of thefirst display device includes locking the first application within thefirst display device that is indicative of preventing a clinician fromtaking any action within the first application.
 20. The system of claim15, wherein the modifying display of the first display device ceases inresponse to the one or more rules no longer being met, the ceasing isindicative of the status of a patient no longer being in a changedstate.